-
Notifications
You must be signed in to change notification settings - Fork 547
Support Progress Flow for McpClient #389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Support Progress Flow for McpClient #389
Conversation
BREAKING : Client Specification record is braking
…Notification to send client progress updates
because of the client code is restored for PR seperation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* @param progressNotification The progress notification to send | ||
* @return A Mono that completes when the notification has been sent | ||
*/ | ||
public Mono<Void> progressNotification(McpSchema.ProgressNotification progressNotification) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be mirrored in the McpSyncServerExchange
@@ -23,6 +23,7 @@ | |||
import io.modelcontextprotocol.util.Assert; | |||
import org.slf4j.Logger; | |||
import org.slf4j.LoggerFactory; | |||
import reactor.util.annotation.Nullable; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove the reactor.util.annotation.Nullable;
@tzolov Thank you for your comment! Yes, the PR depends on #300 and will be rebased after the #300 is merged. I've tried to separate the PR for Server and Client implementation, as the #298 task list. How do you think about this? Do you think separating the PR is meaningful? And do you want a new PR with closing #300 and #389?
Of course! I see the #392, and I can rework to reduce the changes. |
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context